remove direct helium-program-library dep in favor of helium-anchor-gen #575
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lthiery
force-pushed
the
lthiery/helium-anchor-gen
branch
from
2037d4f
to
189db13
Compare
bbalser
approved these changes
Feb 2, 2024
maplant
approved these changes
Feb 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't know if this is a good idea, but I had success doing this on a personal project.
Basically what this does is depend on
helium-anchor-gen(my crate I made this weekend based on a tweet from Noah aboutanchor-gen) instead ofhelium-program-library. The reason to not like HPL is because it has the misfortune of depending onsolana-program-librarywhich pins a bunch of dependencies to patch releases. I think in some effort to workaround this, HPL contains git submodules which I think is what triggers painfully long re-compile times when one must depend on it.Anyway, the way this works is thanks to
anchor-genwhich re-generates Rust structs based on IDL files which are the Anchor build output fromhelium-program-library. So if you're familiar with protobufs, it's as if the Rust code is generating a .proto file and then we generate the Rust code back from the .proto. A bit circular, but au contraire, it breaks the circle and we are no longer infected by the point release pinning of thesolana-program-library.